Infusion Devices and Methods

ABSTRACT

Medical devices, systems, and methods related thereto having hierarchical restrictive access schemes are provided. Such medical devices, systems, and methods may include an in vitro analyte monitoring device, an in vivo analyte monitoring device, and/or a drug infusion device having, among other features, hierarchical permission schemes allowing individual access levels thereto.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 14/730,047 filed Jun. 3, 2015 which is a continuation of U.S. patent application Ser. No. 14/042,629 filed Sep. 30, 2013, which is a continuation of U.S. patent application Ser. No. 11/555,207 filed Oct. 31, 2006, the disclosures of which are incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

A variety of medical devices are employed to monitor a health condition. For example, devices include those designed to enable a user to manage a health condition based at least in part on the level of analyte in the body. These types of devices include analyte determination devices, drug delivery devices, and the like.

Such analyte devices have become widely used in recent years for people with diabetes. Diabetics have typically measured their blood glucose level by lancing a finger tip or other body location (i.e., alternate site) to draw blood, applying the blood to a disposable test strip in a hand-held meter and allowing the meter and strip to perform an electrochemical test of the blood to determine the current glucose concentration. Such discrete or individual, in vitro tests are typically conducted at least several times per day. Detailed descriptions of such glucose monitoring systems and their use are provided in U.S. Pat. No. 7,058,437, issued to TheraSense, Inc., on Jun. 6, 2006, which is incorporated by reference herein in its entirety.

In vivo glucose monitoring devices are designed to provide continuous glucose monitoring. Some of these continuous systems employ a disposable, transcutaneous sensor that is inserted into the skin to measure glucose concentrations in interstitial fluid. A portion of the sensor protrudes from the skin and is coupled with a durable controller and transmitter unit that is attached to the skin with adhesive. A wireless handheld unit is used in combination with the skin-mounted transmitter and sensor to receive glucose readings periodically, such as once a minute. At a predetermined time interval, such as every three, five or seven days, the disposable sensor is removed and replaced with a fresh sensor which is again coupled to the reusable controller and transmitter unit. With this arrangement, a person with diabetes may continuously monitor their glucose level with the handheld unit. The handheld unit of the in vivo system can also include an in vitro test strip meter for conducting individual tests as described above. The in vitro test strip meter can be used to calibrate the continuous monitoring system each time a new in vivo sensor is implanted. Additionally, the in vitro test strip meter can be used as back up in case the in vivo system fails, a new sensor is equilibrating, or when the transmitter must be turned off, such as during takeoffs and landings when aboard an airliner. Detailed descriptions of such a continuous glucose monitoring system and its use are provided in U.S. Pat. No. 6,175,752, which is incorporated by reference herein in its entirety.

Drug delivery devices, including wholly implantable infusion pumps and pumps that infuse drug through a transcutaneously placed fluid channel such as flexible tubing, are devices that enable the controllable administration of a drug to a user. Pumps may be under the control or semi-control of a healthcare monitoring device or may be controlled by the user. Examples of such include insulin pumps used by diabetics to administer insulin for glucose control.

The purpose of in vitro or in vivo glucose monitoring, and insulin delivery devices, is to assist people with diabetes in keeping their blood glucose within a predetermined range. If a person's blood glucose level rises too high, hyperglycemia can occur. The short term effects of hyperglycemia can include fatigue, loss of cognitive ability, mood swings, excessive urination, excessive thirst and excessive hunger. Of more immediate concern, if a person's blood glucose level drops too low, hypoglycemia can occur. Like hyperglycemia, symptoms of hypoglycemia also include fatigue and loss of cognitive ability. If unchecked, however, hypoglycemia can quickly lead to loss of consciousness or coma. Some diabetics have little or no symptoms of hypoglycemia, or find it difficult to distinguish between symptoms of hyperglycemia and hypoglycemia. Long term effects of not keeping blood glucose levels within a proper range include health complications such as cardiovascular disease, chronic renal failure, retinal damage which can lead to blindness, nerve damage, impotence, and gangrene with risk of amputation of toes, feet, and even legs. Clearly, proper glucose monitoring and corrective action based on the monitoring is essential for people with diabetes to maintain their health.

Also of importance is compliance to a glucose monitoring regime. Compliance may be particularly difficult with persons who require supervision, e.g., young children or mentally impaired individuals. Compliance may include strict adherence to healthcare provider and/or caregiver provider instructions. If healthcare instructions change, it is necessary that the user be timely notified of such changes. Likewise, it is important that instructions be readily available in case a person needs to be reminded thereof.

SUMMARY OF THE INVENTION

Before summarizing the invention, it is to be understood that the invention is applicable to in vitro analyte monitoring devices, in vivo analyte monitoring devices, and a drug infusion devices. Unless otherwise indicated, specific reference herein to only one of such devices is only for the sake of brevity and not intended to limit the scope of the invention. Furthermore, the subject invention is described primarily with respect to glucose monitoring devices and insulin infusion pumps, where such descriptions are not intended to limit the scope of the invention. It is to be understood that the subject invention is applicable to any suitable analyte monitoring device and drug infusion device.

According to aspects of some embodiments of the present invention, a medical device (in vitro analyte monitoring device, in vivo analyte monitoring device, drug infusion device) is provided with alert features. These alert features assist a user in maintaining proper analyte levels. Blood glucose is one of many analytes that may be maintained using aspects of the present invention. For each user, an ideal or target analyte range can be established. Above and below this ideal range, upper and lower ranges of moderate concerns, respectively, can also be established. Above the upper range of moderate concern, an upper range of high concern can be established. Similarly, below the lower range of moderate concern, a lower range of high concern can also be established. By way of example, a user can make in vitro blood glucose measurements, such as with a handheld meter and test strip. In some embodiments of the invention, the user can be alerted by the test meter when a measurement falls within either of the upper or lower ranges of moderate concern. The alert may indicate to the user which of the upper and lower ranges of moderate concern the measurement falls into.

According to other aspects of the invention, a medical device (in vitro analyte monitoring device, in vivo analyte monitoring device, drug infusion device) is provided with alarm features. These alarm features also assist a user in maintaining a proper analyte (e.g., blood glucose) level. As described above, upper and lower blood glucose ranges of high concern can be established. In some embodiments of the invention, a test meter can be provided with alarms that warn the user when a measurement falls within either of the upper or lower ranges of high concern. Preferably, the alarm indicates to the user which of the upper and lower ranges of high concern the measurement falls into. Additionally, it is preferable that the alarms indicate a higher level of urgency than do the previously described alerts. Note that a user's analyte level may pass from an ideal range, through a range of moderate concern and into a range of high concern before the user conducts an analyte measurement. In such cases, the user may be provided with an alarm without receiving an alert first.

According to other aspects of the invention, an analyte monitoring system is provided with reminder features. The reminder features also assist a user in maintaining a proper analyte (e.g., glucose) level. Analyte ranges of moderate or high concern can be established, as described above. In some embodiments of the invention, a test meter can have a reminder feature that is triggered when a measurement value falls into a range of moderate or high concern. The reminder can prompt the user after a predetermined period of time to take another analyte measurement to ensure that the analyte level is heading toward or has returned to the ideal range. Such a reminder feature can be particularly helpful since it frees the user from either trying to remember when to retest or from setting an external alarm, if available. For those users that require supervision, such as children, the reminder feature automatically assists the caregiver by providing the user with a retest reminder, even when the caregiver is not present to perform the task of reminding.

According to various aspects of the invention, the above-described alerts, alarms and reminders can be conveyed to the user visually, such as with a graphical user interface (GUI) or light emitting diode(s) (LED). In one embodiment of the invention, a fixed-segment liquid crystal display (LCD) is used as the GUI, with the value of the analyte measurement appearing in flashing numerals when not in the ideal range. In addition, or in an alternative embodiment, up and down arrow icons can be provided to display when an analyte measurement is in the upper or lower range of moderate and/or high concern. For example, a solid arrow icon can be displayed when the level is in the range of moderate concern, and a flashing arrow can be displayed when the level is in the range of high concern. Different icons can be used depending on whether the level is in the range of moderate or high concern. For instance, an arrow icon having a first size can be displayed when the analyte level is in the range of moderate concern, and a larger or vertically displaced arrow icon can be displayed when the level is in the range of high concern. Alternatively, a horizontal arrow can be displayed when the analyte level is in the ideal range, an arrow inclined upward or downward can be displayed when the level is in the upper or lower range of moderate concern, respectively, and an arrow inclined at a steeper upward or downward angle can be displayed when the level is in the upper or lower range of high concern, respectively. Alternatively, the opposite directions of the above arrows can be used to be indicative of the course of action to be taken rather than whether the current level is high or low. For instance, a high analyte level may display a downward pointed arrow to indicate that the user should lower his or her analyte level. In other embodiments, symbols such as +, − and = can be used to indicate high, low and on track readings, respectively. The use of a dot matrix display instead of or in combination with a fixed element display may be employed, e.g., to allow for more flexibility in providing alerts and/or alarms and/or reminders to a user. Text may be shown on the display, with or without accompanying icons, and with or without user feedback, to provide information to the user about a particular alert, alarm and/or reminder. For example, after a test result falling into a range of concern, text may appear explaining the significance of the results, proposing one or more courses of action, and/or indicating that the user should re-test after a certain period of time. After such a period of time has elapsed, a further text message may appear which may include instructions to conduct further tests. Some text messages may be downloaded or otherwise activated as part of a prescription from a Health Care Provider.

To reduce size and/or cost of a meter, one or more LEDs may be used to convey an alert, alarm or reminder to a user. For instance, a single LED can be illuminated when the analyte measurement is not in the ideal range. The LED can be solid when in the range of moderate concern, and flashing when in the range of high concern. Different colors in one or more LEDs can indicate different ranges. For instance green can indicate the analyte level is in the ideal range, yellow can indicate the level is in a range of moderate concern and red can indicate the level is in a range of high concern. Two LEDs can be used to indicate whether the value is high or low (or whether the user's analyte level should be raised or lowered). Three LEDs can be used, for instance with a first LED indicating an analyte level below the ideal range, a second LED indicating a level in the ideal range, and a third LED indicating a level above the ideal range. Four LEDs can be used to indicate an analyte level in the lower range of high concern, the lower range of moderate concern, the upper range of moderate concern and the upper range of high concern, respectively. A fifth LED can be added to indicate a level in the ideal range.

In addition to or instead of visual indicators of alerts, alarms and reminders, a glucometer constructed according to aspects of the present invention can incorporate audible or physical feedback. Since diabetes can adversely affect a person's eyesight, such forms of user interface can become necessary. In one embodiment of the invention, a meter can emit an audible tone to indicate an analyte reading that is outside of the ideal range. A high tone can be used to indicate a reading that is above the ideal range while a low tone can be used to indicate a reading that is below. A pulsing or intermittent tone can be used to indicate a reading that is in a range of high concern. A varying number of pulses and other variations can be employed to indicate what range the analyte reading is in. Similarly, a vibratory signal, such as used in cell phones, can be used with different variations for indicating alerts, alarms and reminders to a user.

According to various aspects of the invention, the above-described alerts, alarms and reminders can be set with default parameters during manufacture, and/or may be settable by a HCP (Health Care Professional such as a Doctor or Certified Diabetes Educator) with levels corresponding to prescribed values for a user, and/or may be user configurable. In one embodiment of the invention, a meter is provided that is set to automatically remind the user to retest after a predetermined period of time, which may be preset or configured, after a test that falls outside of an ideal analyte range. The meter may be configured to allow the user or healthcare professional to disable this feature. In an alternative embodiment, the meter is provided “out of the box” with such a reminder feature disabled, but with provisions to allow the user or healthcare professional to enable it and/or set configuration parameters. A meter can be provided that allows different reminder parameters depending on whether the underlying analyte measurement is in a range of moderate concern or a range of high concern. In one embodiment, the medical device reminds the user with a first audible signal to retest a first time period (e.g. about 30 minutes) after a test result falling in a range of moderate concern, and reminds the user with a second audible signal to retest after a second time period (e.g. about 15 minutes) after a test result falling in a range of high concern. In certain embodiments, the second audible signal has a higher volume level and/or longer duration than the first audible signal, and the second time period may be shorter than the first time period. In this embodiment, the second audible signal can also be accompanied with a vibratory signal. In this or alternative embodiments, the first and/or second signals can continue or repeat if not acknowledged by the user, such as with the push of a button, or with an actual test being conducted. The parameters of the reminders can also be different based on whether the analyte reading is above or below the ideal range, and/or can vary depending on the actual value of the analyte measurement. For each reminder (alert or alarm) the settings may include, but are not limited to, the analyte value, time to reminder, type of reminder (e.g. visual, audible, vibratory, or a combination thereof), persistence of the reminder (e.g. once, once a minute for n times, or once a minute until acknowledged), and the number of times (n) a persistent reminder will repeat.

According to certain embodiments, a medical device can be provided with alert, alarm and reminder settings, or other healthcare information that can be configured and locked by an authorized individual such as an individual in a supervisory role, e.g., a HCP or caregiver. The information may be locked until an access code is supplied, such as by an authorized individual, e.g., a HCP or a caregiver. Such an arrangement prevents those under the care of a HCP from changing a prescription or those receiving guidance from a caregiver, for instance children, from modifying configuration values. This prevents intentional or unintentional changes to the configuration values. It also prevents the bypassing of alerts, alarms or reminders, such as when a user wants to engage in behavior that may affect analyte levels, e.g., eat improperly. According to other aspects, configuration settings may be set through a medical device data port, such as when the medical device is connected to a computer for the uploading and/or downloading of information. In certain embodiments, a medical device may be configured to enable a limited number of individuals, e.g., HCP and/or a caregiver, to set and lock configuration values through the data port.

Application of the inventive aspects described herein is not limited to blood glucose monitoring and/or insulin infusion. For example, analytes may be monitored in other substances such as interstitial fluid. Moreover, monitoring of analytes other than glucose, such as lactate, acetyl choline, amylase, bilirubin, cholesterol, chorionic gonadotropin, creatine kinase (e.g., CK-MB), creatine, DNA, fructosamine, glucose, glutamine, growth hormones, hematocrit, hemoglobin (e.g. HbA1c), hormones, ketones, lactate, oxygen, peroxide, prostate-specific antigen, prothrombin, RNA, thyroid stimulating hormone, and troponin, in samples of body fluid. Meters may also be configured to determine the concentration of drugs, such as, for example, antibiotics (e.g., gentamicin, vancomycin, and the like), digitoxin, digoxin, drugs of abuse, theophylline, warfarin and the like. Such analytes can be monitored in blood, interstitial fluid, saliva, urine and other bodily fluids. It should also be noted that fewer or additional analyte measurement ranges from those described herein can be used. This includes not using ranges at all, but instead using, e.g., absolute values, formulas, lookup tables or similar concepts known to those skilled in the art to determine if or what type of alert, alarm, reminder or other indication should be made to the user for a particular analyte measurement result.

BRIEF DESCRIPTION OF THE DRAWINGS

Each of the figures diagrammatically illustrates aspects of the invention. Of these:

FIG. 1 is plan view showing an exemplary embodiment of an analyte monitoring system, such as a glucometer system, constructed according to aspects of the present invention;

FIG. 2 is a block diagram of an exemplary embodiment of an insulin delivery device;

FIG. 3 is a block diagram illustrating an exemplary embodiment of an insulin therapy management system that incorporates the delivery device of FIG. 2;

FIG. 4 is a detail example of various alert and alarm displays, one of which is shown in the system of FIG. 1;

FIG. 5 is a graph depicting an example of how the glucose level of a user might vary over the course of a portion of a day;

FIG. 6 is a graph depicting the glucose levels shown in FIG. 3 with testing points added, some of which occur as a result of a reminder (alert or alarm);

FIGS. 7A and 7B show exemplary embodiments of a medical device with restrictive user control;

FIG. 8 shows the medical device of FIG. 7B connected to an exemplary embodiment of a data management system; and

FIG. 9 shows an exemplary embodiment of application software that may run on the data management system of FIG. 8.

Variation of the invention from that shown in the figures is contemplated.

DETAILED DESCRIPTION

The following description focuses on one variation of the present invention. The variation of the invention is to be taken as a non-limiting example. It is to be understood that the invention is not limited to particular variation(s) set forth and may, of course, vary. Changes may be made to the invention described and equivalents may be substituted (both presently known and future-developed) without departing from the true spirit and scope of the invention. In addition, modifications may be made to adapt a particular situation, material, composition of matter, process, process act(s) or step(s) to the objective(s), spirit or scope of the present invention.

FIG. 1 shows a top view of an exemplary analyte medical system 10, e.g., a glucometer system in this particular embodiment. Analyte medical device 10 may be an electrochemical or optical system. System 10 includes a handheld meter 12 and disposable test strip 14. Test strip 14 can be inserted into or removed from test strip port 16 of meter 12 for physical and electrical interconnection therewith. Meter 12 includes an LCD display 18 for displaying information to the meter user, and buttons 20, 22 and 24 for receiving input from the user.

In general, to take a blood glucose measurement with meter 12, a user inserts a new test strip 14 into port 16 of meter 12. Either before of after strip insertion into the meter, a user then lances a fingertip or other part of the body (i.e. alternate site) to draw a small drop of blood 26 to the surface of the skin. The meter and strip are positioned over the drop of blood 26 so that one of the sample chamber ends 28 is touching the drop of blood 26. While this particular example teaches the use of a side-fill strip, it should be noted that an end-fill, top-fill or other type of test strip may be utilized. Moreover, the analyte testing need not use a test strip at all. For instance, certain test meters may utilize a rotary test wheel for making multiple measurements, rather than individual test strips. In the present example, surface tension (wicking) automatically draws a small amount of blood 26 into the sample chamber and an electrochemical test is automatically performed by meter 12 to determine the glucose concentration in the blood 26. The glucose level 30 is then displayed on meter 12. As noted above, the subject invention is also applicable to continuous analyte monitoring systems and drug infusion devices.

The present invention may also find use with infusion systems for infusing an agent to a user such as drug infusion systems, e.g., insulin infusion systems. Such infusion systems may be wholly implantable systems or external systems. External infusion devices are typically connected to an infusion set which includes a cannula that is placed transcutaneously through the skin of the patient to infuse a select dosage of an agent. For example, external insulin infusion devices are typically connected to an infusion set which includes a cannula that is placed transcutaneously through the skin of the patient to infuse a select dosage of insulin based on the infusion device's programmed basal rates or any other infusion rates as prescribed by the patient's HCP. A user may be able to control the insulin pump device to administer additional doses of insulin during the course of wearing and operating the infusion device such as for, administering a carbohydrate bolus prior to a meal. Certain infusion devices may include a food database that has associated therewith, an amount of carbohydrate, so that the patient may better estimate the level of insulin dosage needed for, for example, calculating a bolus amount.

FIG. 2 is a block diagram of an exemplary embodiment of an insulin delivery for use with the present invention. Insulin delivery device 620 in one embodiment includes a processor 710 operatively coupled to a memory unit 740, an input unit 720, a display unit 730, an output unit 760, and a fluid delivery unit 750. In one embodiment, the processor 710 includes a microprocessor that is configured for and capable of controlling the functions of the insulin delivery device 620 by controlling and/or accessing each of the various components of the insulin delivery device 620. In one embodiment, multiple processors may be provided as safety measure and to provide redundancy in case of a single processor failure. Moreover, processing capabilities may be shared between multiple processor units within the insulin delivery device 620 such that pump functions and/or control may be performed faster and more accurately.

Input unit 720 operatively coupled to the processor 710 may include a jog dial, key pad buttons, a touch pad screen, or any other suitable input mechanism for providing input commands to the insulin delivery device 620. More specifically, in case of a jog dial input device, or a touch pad screen, for example, the patient or user of the insulin delivery device 620 may manipulate the respective jog dial or touch pad in conjunction with the display unit 730 which performs as both a data input and output unit. The display unit 730 may include a touch sensitive screen, an LCD screen, or any other types of suitable display unit for the insulin delivery device 620 that is configured to display alphanumeric data as well as pictorial information such as icons associated with one or more predefined states of the insulin delivery device 620, or graphical representation of data such as trend charts and graphs associated with the insulin infusion rates, trend data of monitored glucose levels over a period of time, or textual notification to the patients.

Output unit 760 operatively coupled to the processor 710 may include an audible alarm including one or more tones and/or preprogrammed or programmable tunes or audio clips, or vibratory alert features having one or more pre-programmed or programmable vibratory alert levels. In one embodiment, the vibratory alert may also assist in priming the infusion tubing to minimize the potential for air or other undesirable material in the infusion tubing. Also shown is the fluid delivery unit 750 which is operatively coupled to the processor 710 and configured to deliver the insulin doses or amounts to the patient from the insulin reservoir or any other types of suitable containment for insulin to be delivered (not shown) in the insulin delivery device 620 via an infusion set coupled to a subcutaneously positioned cannula under the skin of the patient.

Memory unit 740 may include one or more of a random access memory (RAM), read only memory (ROM), or any other types of data storage units that is configured to store data as well as program instructions for access by the processor 710 and execution to control the insulin delivery device 620 and/or to perform data processing based on data received from, e.g., an analyte monitoring system 610, a remote terminal 640 (HCP or caregiver), the patient 630 or any other data input source (see for example FIG. 3).

FIG. 3 is a block diagram illustrating an insulin therapy management system 600 that includes an insulin infusion device and an analyte monitoring system. The insulin therapy management system 600 includes an analyte monitoring system 610 operatively coupled to an insulin delivery device 620, which may be in turn, be operatively coupled to a remote terminal 640. Analyte monitoring system 610 is, in one embodiment, coupled to the patient 630 so as to monitor or measure the analyte levels of the patient. Moreover, the insulin delivery device 620 is coupled to the patient using, for example, an infusion set and tubing connected to a cannula (not shown) that is placed transcutaneously through the skin of the patient so as to infuse medication such as, for example, insulin, to the patient.

In one embodiment, the analyte monitoring system 610 may include one or more analyte sensors subcutaneously positioned such that at least a portion of the analyte sensors are maintained in fluid contact with the patient's analytes. The analyte sensors may include, but not limited to short term subcutaneous analyte sensors or transdermal analyte sensors, for example, which are configured to detect analyte levels of a patient over a predetermined time period, and after which, a replacement of the sensors is necessary.

The one or more analyte sensors of the analyte monitoring system 610 is coupled to a respective one or more of a data transmitter unit which is configured to receive one or more signals from the respective analyte sensors corresponding to the detected analyte levels of the patient, and to transmit the information corresponding to the detected analyte levels to a receiver device, and/or insulin delivery device 620. That is, over a communication link, the transmitter units may be configured to transmit data associated with the detected analyte levels periodically, and/or intermittently and repeatedly to one or more other devices such as the insulin delivery device and/or the remote terminal 640 for further data processing and analysis. The transmitter units of the analyte monitoring system 610 may be, in one embodiment, configured to transmit the analyte related data substantially in real time to the insulin delivery device 620 and/or the remote terminal 640 after receiving it from the corresponding analyte sensors such that the analyte level such as glucose level of the patient 630 may be monitored in real time.

The transmitter units of the analyte monitoring system 610 may be configured to directly communicate with one or more of the remote terminal 640 or the insulin delivery device 620. Furthermore, within the scope of the present invention, additional devices may be provided for communication in the insulin therapy management system 600 including additional receiver/data processing unit, remote terminals (such as a HCP terminal and/or a bedside terminal in a hospital environment, for example).

The insulin delivery device 620 may include in one embodiment, but is not limited to, an external infusion device such as an external insulin infusion pump, an implantable pump, a pen-type insulin injector device, a patch pump, an inhalable infusion device for nasal insulin delivery, or any other type of suitable delivery system.

In one embodiment, the analyte monitoring system 610 includes a strip port configured to receive a test strip for capillary blood glucose testing. In one aspect, the glucose level measured using the test strip may in addition, be configured to provide periodic calibration of the analyte sensors of the analyte monitoring system 610 to assure and improve the accuracy of the analyte levels detected by the analyte sensors.

Exemplary in vitro and in vivo analyte monitoring system and drug infusion systems that may be adapted for the present invention include, but are not limited to, those described in U.S. Pat. Nos. 6,175,752; 6,329,161; 6,284,478; 6,916,159; 7,041,468; 7,077,328, and U.S. patent application Ser. Nos. 11/383,945; 11/365,168; 11/386,915; 11/396,181; 11/396,182, and elsewhere, the disclosures of which are herein incorporated in their entirety by reference.

According to aspects of the present invention, an alert and/or alarm 32 can also be shown on display 18 indicating, for example, whether the current measurement falls within a predetermined range, such as an ideal glucose range, an upper or lower range of moderate concern or an upper or lower range of high concern.

Referring now to FIG. 4, a further example of alert and alarm displays 32 is shown. A steeply downwardly inclined arrow 34 (e.g. from about −60 to about −90 degrees) can be used to indicate a glucose reading in a lower range of high concern, such as below 50 mg/dL. A moderately downwardly inclined arrow 36 (e.g. from about −30 to about −45 degrees) can be used to indicate a glucose reading in a lower range of moderate concern, such as about 50 mg/dL to about 75 mg/dL. A horizontal arrow 38 (e.g. about 0 degrees) can be used to indicate a glucose reading in an ideal range, such as about 75 mg/dL to about 175 mg/dL. A moderately upwardly inclined arrow 40 (e.g. about 30 or about 45 degrees) can be used to indicate a glucose reading in an upper range of moderate concern, such as about 175 mg/dL to about 250 mg/dL. Finally, a steeply upwardly inclined arrow 42 (e.g. from about 60 to about 90 degrees) can be used to indicate a glucose reading in an upper range of high concern, such as above about 250 mg/dL. As previously indicated above, various other visual elements, and/or audible or physical indicators can be used to provide the user with an alert or an alarm.

Referring now to FIG. 5, an example of blood glucose values for a user is shown. Curve 100 depicts how the user's blood glucose might change with time over a portion of a day. In this example, the ideal range for the user is about 75 mg/dL to about 175 mg/dL, shown with reference numeral 110 and bounded by dashed lines 112 and 114. The ranges of moderate concern are about 50 mg/dL to about 75 mg/dL (lower alert zone 116, bounded by dashed lines 112 and 118) and about 175 mg/dL to about 250 mg/dL (upper alert zone 120, bounded by dashed lines 114 and 122). The ranges of high concern are below about 50 mg/dL (lower alarm zone 124, below dashed line 118) and above about 250 mg/dL (upper alarm zone 126, above dashed line 122).

In FIG. 5 the glucose values (100) begin at about 150 mg/dL, rise to about 195 mg/dL (101), fall to about 155 mg/dL (102), rise to about 270 mg/dL (103), fall to about 60 mg/dL (104), rise to about 90 mg/dL (105), fall to about 40 mg/dL (106), and end at about 100 mg/dL.

FIG. 6 shows the same blood glucose values 100 as FIG. 5 but adds the testing that was performed by that user, some of which occurs as a result of a reminder (alert and/or alarm and/or reminder). For example, after a light meal (snack) the user tests with a reading of 193 mg/dL (201) that falls in the upper alert zone (120). This reading may cause meter 12 to generate an alert to the user, e.g., flashing display, beep, or the like, that his or her glucose is in an upper level of moderate concern, as previously described above. The meter may alert the user substantially immediately after the determination of the reading in the upper alert zone, or sometime thereafter as described below. Regardless of whether the user is notified substantially immediately of a reading in an alert zone (or other zone of concern as described herein), the meter may also be configured to remind the user to perform a re-test after a predetermined amount of time following a reading in a zone of importance (alarm zone or alert zone). For example, after the above-described meter reading in upper alert zone 120, a meter reminder may notify the user to perform a test after a predetermined amount of time, e.g., about 5 minutes, e.g., about 10 minutes, e.g., about 20 minutes, e.g., about 30 minutes, etc., and may periodically remind a user until a test is performed or until the reminder is cleared by the user. For example, the user may respond to the reading and alert (if alerted) with modest therapy and some time later (e.g., about 30 minutes), a reminder prompts the user to test, resulting in a reading of 160 mg/dL (202) that falls in the ideal zone (110).

Later, after a large meal the user tests with a reading of 268 mg/dL (203) that falls in the upper alarm zone (126). This reading causes meter 12 to generate an alarm to the user that his or her glucose is in an upper level of high concern. The user responds to the reading with an appropriate therapy and some time later (e.g. 20 minutes), a reminder prompts the user to test, resulting in a reading of 232 mg/dL (204) that falls in the upper alert zone (120). This reading causes meter 12 to generate an alert to the user that his or her glucose is in an upper level of moderate concern. The user may note that the previous therapy was appropriate and again, some time later (e.g. 30 minutes), a reminder prompts the user to test again, resulting in a reading of 156 mg/dL (205) that falls in the ideal zone (110) and confirms the previous therapy was appropriate.

Still later, after having exercised but not having eaten the user feels slightly symptomatic and tests with a reading of 61 mg/dL (206) that falls in the lower alert zone (116). This reading causes meter 12 to generate an alert to the user that his or her glucose is in a lower level of moderate concern. The user responds by eating a light meal (snack) and some time later (e.g. 25 minutes), a reminder prompts the user to test, resulting in a reading of 81 mg/dL (207) that falls in the ideal zone (110).

Yet later still, the user feels symptomatic and tests with a reading of 41 mg/dL (208) that falls in the lower alarm zone (124). This reading causes meter 12 to generate an alarm indicating that the glucose level is in a lower level of high concern. The user responds by eating a modest meal and some time later (e.g. 15 minutes), a reminder prompts the user to test, resulting in a reading of 63 mg/dL (209) that falls in the lower alert zone (116). This reading causes meter 12 to generate an alert indicating that the glucose level is now in a lower level of moderate concern. The user may note that the previous therapy (meal) was appropriate or may eat a small amount (snack) and again some time later (e.g. 25 minutes), a reminder prompts the user to test, resulting in a reading of 99 mg/dL (210) that falls in the ideal zone (110) and confirms the course of therapy was appropriate.

It should be noted that in this example, tests 201, 203, 206 and 208 were initiated by the user based on events known by the user to cause changes in blood glucose, or based on symptoms experienced by the user. More importantly, the user was prompted to perform tests 202, 204, 205, 207, 209 and 210 by a meter constructed according to aspects of the present invention. These prompts or timed reminders assist the user in performing appropriate tests in a timely manner. These tests in turn facilitate the user's important goal of keeping his or her blood glucose level in the ideal zone 110 to maintain the user's short-term and long-term health.

Embodiments also include supervisor-controllable, including person-restrictive (e.g., user-restrictive), medical devices. Configurations of a medical device may be settable and/or lockable by a supervisor (e.g., a HCP, parent or guardian, caregiver, or the like), e.g., remotely or by direct action (e.g., using a user interface of the device, or the like). For example, certain configurations of a medical device may be settable and/or lockable by a first person (e.g., a HCP) having a first access level (e.g., full access such as full Read/Write permission) and certain configurations that may be settable and/or lockable by a second person (e.g., a caregiver) having a second access level (e.g., limited Read/Write permission). The medical device may be settable and/or lockable by a third person (e.g., a user under the supervision of the first and second persons) having a third access level (e.g., further limited, e.g., Read only—including no rights to modify previously inputted data). Any number of persons may have certain or limited access rights to a medical device. For example, certain embodiments include medical devices having certain configurations settable and/or lockable by a HCP and certain other features settable and/or lockable by a caregiver. A user may be completely restricted from modifying the configurations set by the HCP and/or caregiver.

Configurations may be access controlled with an access code (e.g., password protected, voice authentication, USB token protected, or other manner of authenticating a user) to allow access permissions for a specific individual, medical device, computer, or group of individuals. When permission is set, the type and level of access granted to an individual, computer, or group is granted. For example, various degrees of, e.g., Read and Write and View permissions may be granted to different persons, as described above.

Different codes may provide different rights. For example an HCP code may enable a HCP to enter prescriptive information and/or delete and/or modify stored prescriptive (“Rx”) information, where prescriptive information is broadly defined relevant information prescribed by a HCP. Prescriptive information may include patient-specific data and may include but is not limited to, one or a plurality of basal rates, insulin ideal analyte ranges, alert and alarm thresholds, medication type (e.g., insulin type), medication dose including total daily dose (e.g., total daily insulin dosage), drug sensitivity (e.g., insulin sensitivity), when to take a medication, how to take a medication, when to treat a condition, how to treat a condition, when to elevate concerns to a HCP or caregiver, reminder schemes (e.g., setting times of reminders), etc. The above is not an exhaustive list, e.g., for treating diabetes, information may also include insulin/carbohydrate information, and other relevant information. In this manner, a medical device may be customizable by a HCP to include user-specific prescriptive information, some of which may not relate to values or settings in the medical device but may be made available for reference purposes only (e.g., as a text note such as those commonly displayed on a PDA, or the like). A medical device may be lockable by a HCP, who may also set access levels for others such as for a caregiver and/or user. In this manner, a HCP (or other designated individual) may serve as the “Administrator” having the ability to control access at a granular level, establishing access levels on a person-by-person basis.

In addition to, or instead of HCP provided configurations, a caregiver may also enter and/or lock configurations of a medical device. In many embodiments, at least some of the configurations under caregiver control differ at least in part from configurations reserved for HCP control, which would be prescriptive in nature, as described above. Caregiver access may enable a caregiver to enter caregiver information and/or delete and/or modify stored caregiver information. Caregiver information includes, but is not limited to the ability to set and lock any value or user restriction not previously set and locked by the HCP such as non-prescriptive alarm values, user menu access, and other user privileges such as data transfer (e.g., upload to a PC) and storage options (e.g., read-only or read-write access to various data). For example, a HCP may set and lock values and allowed options (e.g., lock menus). The caregiver access allowed by the HCP can set and lock that which the HCP did not lock. Caregiver access may provide the caregiver with the ability to lock and/or unlock user features, such as providing the user with increased access over time as the user begins to understand and appreciate the subtleties and complexities of various features (e.g., setting correct values such as alarm thresholds and reminder time values or accessing menus that show information that might be confusing if not interpreted properly). Similarly, the user may be able to access that allowed by the caregiver (and HCP), and may be able to set that which is not locked.

The configurations may be set and/or locked by inputting data directly into the medical device using, e.g., a user interface, or may be accomplished indirectly including remotely, e.g., via a computer system connected to a network, where a network represents any uni- or bi-directional communication link suitable for communicating data, such as a wide-area network, local area network, or a global computer network like the World Wide Web (“the Web”). Accordingly, embodiments include a web-based data management system that allows persons to controllably access and/or manipulate and/or share information, depending on a given person's permission level. Each HCP and/or caregiver and/or medical device user may interact with a computing device suitable for accessing the data management system via a network. For example, a personal computer, laptop computer, phone such as a cellular telephone, a personal digital assistant (PDA), etc., may be used. The communication device typically executes communication software, typically a web browser such as INTERNET EXPLORER from Microsoft Corporation of Redmond, Wash., or the like, in order to communicate with the data management system.

Once configurations are set, e.g., by a HCP, caregiver or user, the stored information may be employed by the medical device in the execution of healthcare management, e.g., glucose monitoring. The stored information may be conveyed to a user in audible format and/or visual and/or tactile format. For example, prescriptive information inputted by a HCP may be visually displayed on the display of a medical device, e.g., as an icon (e.g., an “Rx” icon, as a note (similar to displayed PDF notes), or the like), or may be in audible or tactile form.

FIG. 7A shows the hierarchal permission scheme of an embodiment of a medical device 300 having restrictive control, e.g., restrictive caregiver and user control. The most critical settings and portions of the user interface (e.g. the ability to set values and activate menu items) may be set by a HCP. Values that must be prescribed by a HCP are in the HCP Only portion of the user interface as bounded by the dashed line 310. Additional values prescribed by the HCP are included in the HCP settings region 320 as bounded by the solid line 330. For example, the HCP may restrict access to various options and menus (e.g., data transfer and storage parameters) and may set and lock various values such as, for example, the lower threshold for high concern and the associated alarm parameters. A caregiver (e.g. a parent) may set additional restrictions by the Caregiver settings region 340 as bounded by the solid line 350. For example, the caregiver may set and lock the previously unlocked upper threshold for high concern and the associated alarm parameters and set preferred values for other threshold and the associated alarm parameters without locking those values (i.e., the user may update those values at a later time). Finally, the user of the medical device is allowed access to the User Allowed portion of the user interface as bounded by the dashed line 360 along with a portion of the user interface that is always allowed, which is included in the User region 370 of the user interface.

FIG. 7B shows medical device 300 of FIG. 7A, but in this embodiments there is no caregiver and the User region 370 includes of all portions of the user interface that are not restricted by the HCP in the HCP settings region 320.

FIG. 8 shows medical device 300 as connected to a Data Management System (DMS) 400 through connection 410 which may be wired or wireless. The DMS 400 may interface too many medical devices where only one is shown, and each may be of similar or differing types (e.g. analyte meter (such as a blood glucose meter), continuous analyte monitor (such as a continuous glucose monitor), or drug infusion pump (such as an insulin pump)).

FIG. 9 shows application software (SW) that runs on the DMS 400 where the DMS Application SW 500 interfaces to the medical device (not shown) via connection 410. SW 500 may be embodied on a computer readable medium. The DMS Application SW 500 also interfaces to the HCP Application SW 510, the Caregiver Application SW 520, and the User Application SW 530 through SW connections 540, 550 and 560 respectively. Each of the HCP, Caregiver and User Application SW modules has the same restrictive user controls (e.g. privileges and restrictions) to those that are set directly on the medical device while allowing a more complete user interface, such as a Graphical User Interface (GUI) such as those commonly found on PC computers. Additional features available only on the DMS 400 through the GUI (e.g. advanced data graphing features) may also be subject to similar restrictive user controls as described for the medical device.

As for additional details pertinent to the present invention, materials and manufacturing techniques may be employed as within the level of those with skill in the relevant art. The same may hold true with respect to method-based aspects of the invention in terms of additional acts commonly or logically employed. Also, it is contemplated that any optional feature of the inventive variations described may be set forth and claimed independently, or in combination with any one or more of the features described herein. Likewise, reference to a singular item, includes the possibility that there are plural of the same items present. More specifically, as used herein and in the appended claims, the singular forms “a,” “an,” “said,” and “the” include plural referents unless the context clearly dictates otherwise. It is further noted that the claims may be drafted to exclude any optional element. As such, this statement is intended to serve as antecedent basis for use of such exclusive terminology as “solely,” “only” and the like in connection with the recitation of claim elements, or use of a “negative” limitation. Unless defined otherwise herein, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The breadth of the present invention is not to be limited by the subject specification, but rather only by the plain meaning of the claim terms employed. 

1. A medical device comprising: one or more processors; and a memory unit operatively coupled to the one or more processors and including programming stored therein which, when executed by the one or more processors, causes the one or more processors to provide individual hierarchical access level rights including at least first access level rights, second access level rights, and third access level rights, wherein the first access level rights enable a first individual to modify, set, or lock first level parameters of the medical device, wherein the second access level rights enable a second individual to set, modify, or lock second level parameters of the medical device, the second parameters at least being different than first level parameters locked by the first individual, and wherein the third access level rights enable a third individual to set, modify, or lock third level parameters of the medical device, the third parameters being at least different than the first level parameters locked by the first individual and the second level parameters locked by the second individual.
 2. The medical device of claim 1, wherein at least a portion of the first level parameters are prescriptive parameters, and wherein the programming, when executed by the one or more processors, causes the one or more processors to prevent both the second individual having second access level rights and the third individual having third access level rights from setting, modifying, or locking the prescriptive parameters.
 3. The medical device of claim 2, wherein the prescriptive parameters are one or more of a basal rate, an insulin ideal analyte range, an alert or alarm threshold, a medication type, a medication dose, a total daily medication dose, a drug sensitivity, a parameter associated with when to take mediation, a parameter associated with how to take medication, a parameter associated with when to treat a condition, a parameter associated with how to treat the condition, and a reminder scheme.
 4. The medical device of claim 1, wherein the second level parameters and the third level parameters are non-prescriptive parameters.
 5. The medical device of claim 4, wherein the non-prescriptive parameters are one or more of a non-prescriptive alarm value, a user menu access parameter, and a data transfer and storage parameter.
 6. The medical device of claim 1, wherein one or more of the first level parameters, second level parameters, and third level parameters includes an alarm, alert, or reminder associated therewith.
 7. The medical device of claim 1, further comprising a fluid delivery unit.
 8. The medical device of claim 7, wherein the fluid delivery unit is operatively coupled to the one or more processors and including programming stored therein which, when executed by the one or more processors, causes the one or more processors to access and control the fluid delivery unit.
 9. The medical device of claim 7, wherein the fluid delivery unit is an insulin delivery device.
 10. The medical device of claim 1, further comprising at least one of an input display unit and an output display unit.
 11. The medical device of claim 1, wherein the medical device is in data communication with an analyte monitoring device.
 12. A medical device comprising: a fluid delivery unit; an input display unit; an output display unit; one or more processors; and a memory unit operatively coupled to the one or more processors and including programming stored therein which, when executed by the one or more processors, causes the one or more processors to provide individual hierarchical access level rights including at least first access level rights, second access level rights, and third access level rights, wherein the first access level rights enable a first individual to modify, set, or lock first level parameters of the medical device, wherein the second access level rights enable a second individual to set, modify, or lock second level parameters of the medical device, the second parameters at least being different than first level parameters locked by the first individual, and wherein the third access level rights enable a third individual to set, modify, or lock third level parameters of the medical device, the third parameters being at least different than the first level parameters locked by the first individual and the second level parameters locked by the second individual.
 13. The medical device of claim 12, wherein at least a portion of the first level parameters are prescriptive parameters, and wherein the programming, when executed by the one or more processors, causes the one or more processors to prevent both the second individual having second access level rights and the third individual having third access level rights from setting, modifying, or locking the prescriptive parameters.
 14. The medical device of claim 13, wherein the prescriptive parameters are one or more of a basal rate, an insulin ideal analyte range, an alert or alarm threshold, a medication type, a medication dose, a total daily medication dose, a drug sensitivity, a parameter associated with when to take mediation, a parameter associated with how to take medication, a parameter associated with when to treat a condition, a parameter associated with how to treat the condition, and a reminder scheme.
 15. The medical device of claim 12, wherein the second level parameters and the third level parameters are non-prescriptive parameters.
 16. The medical device of claim 15, wherein the non-prescriptive parameters are one or more of a non-prescriptive alarm value, a user menu access parameter, and a data transfer and storage parameter.
 17. The medical device of claim 12, wherein one or more of the first level parameters, second level parameters, and third level parameters includes an alarm, alert, or reminder associated therewith.
 18. The medical device of claim 12, wherein the fluid delivery unit is operatively coupled to the one or more processors and including programming stored therein which, when executed by the one or more processors, causes the one or more processors to access and control the fluid delivery unit.
 19. The medical device of claim 12, wherein the fluid delivery unit is an insulin delivery device.
 20. The medical device of claim 12, wherein the medical device is in data communication with an analyte monitoring device. 